Loop Maintenance is a framework developed by Warren C. Sholtz for reading and correcting drift in any system built on repeated interaction — teams, relationships, organizations, and communication systems generally. Its central claim: most of what gets diagnosed as a "people problem" — friction, disengagement, breakdowns in trust — is actually a structural drift problem, invisible until it accumulates.
The same underlying mechanism applies whether the system in question is a two-person relationship, a management hierarchy, or an organization of thousands.
The Problem It Solves
When something feels wrong between people but nothing specific happened, the most available explanations are personal — chemistry, resilience, leadership style. Loop Maintenance reframes the question: not "who's the problem," but "where is the loop not completing, and what's accumulating as a result?" This turns an invisible, diffuse discomfort into something specific enough to actually address.
Core Concepts Within Loop Maintenance
Drift
The quiet, compounding accumulation of small uncorrected mismatches. Rarely caused by one event; almost always the residue of many small ones.
The Three Structural Maintenance Elements
Direction, Constraint, and Shared Reference Points. Systems stay level when these three stay current; they drift when any one goes stale.
Multi-Level Reading
Drift can be diagnosed at the individual/practitioner level, the supervisory/relational level, and the organization-wide level. A full diagnosis checks all three, since they compound each other.
Structural vs. Personal Misdiagnosis
Organizations and relationships consistently mistake structural drift for a personal or character issue, because drift is invisible until it's significant, and the people closest to it are usually the ones least able to see it from outside.
Practical Examples
A team that "just doesn't communicate well anymore," despite no specific incident — often direction or reference-point drift, not a personality mismatch.
Frontline concerns that quietly stop reaching leadership in their original form — a structural drift pattern, not a loyalty or communication-skills issue.
A long-standing professional relationship that's become effortful for no nameable reason — accumulated drift in the shared interaction surface between two people.
Founder Notes
Warren developed Loop Maintenance in parallel with Tina's work on SOMA, applying the same underlying architecture — how systems that predict and respond over time either stay aligned or quietly drift — across many different domains at once: teams, personal relationships, internal self-regulation, organizational systems, and even AI/LLM interaction. The consistent finding across every domain: the same structural skeleton, expressed in domain-appropriate language.